@vtavana
For some reason, including the project.license field in pyproject.toml causes builds to fail citing [REDACTED: solved the problem, setuptools needed to be pinned in the CI, oops!]

configuration error: `project.license` must be valid exactly by one definition (2 matches found):

    - keys:
        'file': {type: string}
      required: ['file']
    - keys:
        'text': {type: string}
      required: ['text']

did you see this at all with mkl_fft? Only happens in CI as well...

@ekomarova
I've updated the build scripts here (similar to some previous changes in mkl_fft) to avoid directly calling setup.py since it's been deprecated for years anyway

Thanks, @ndgrigorian! As soon as there is a tag that includes these changes, I can rebuild mkl_random to include this in the internal recipe

@antonwolfy
ping

@antonwolfy @vtavana
build/tests fixed again, I'll follow up with another PR to fix more warnings. Also not sure what is causing these expected checks, but I'd like this PR to not get too big, it's ready for more review

The expected checks are present because of a change in the naming of the workflow in https://github.com/IntelPython/mkl_random/pull/65/files
and these expected checks are tagged as required with their old names.

You can remove them from the required list in the setting (and add the equivalent one with the new name). I do not have access to setting in this repo.

Settings > Rules > Rulesets > Repository rulesets > Require status checks to pass > show additional settings

The expected checks are present because of a change in the naming of the workflow in https://github.com/IntelPython/mkl_random/pull/65/files and these expected checks are tagged as required with their old names.

Good call, this was the issue, thanks